Vcenter NamespaceManagement Clusters EnableSpec
The Vcenter NamespaceManagement Clusters EnableSpec schema contains the specification required to enable vSphere Namespaces on a cluster.
This schema was added in vSphere API 7.0.0.0.
{
"size_hint": "string",
"service_cidr": {
"address": "string",
"prefix": 0
},
"network_provider": "string",
"ncp_cluster_network_spec": {
"pod_cidrs": [
{
"address": "string",
"prefix": 0
}
],
"ingress_cidrs": [
{
"address": "string",
"prefix": 0
}
],
"egress_cidrs": [
{
"address": "string",
"prefix": 0
}
],
"cluster_distributed_switch": "string",
"nsx_edge_cluster": "string",
"nsx_tier0_gateway": "string",
"namespace_subnet_prefix": 0,
"routed_mode": false
},
"workload_networks_spec": {
"supervisor_primary_workload_network": {
"network": "string",
"network_provider": "string",
"vsphere_network": {
"portgroup": "string",
"ip_assignment_mode": "string",
"address_ranges": [
{
"address": "string",
"count": 0
}
],
"gateway": "string",
"subnet_mask": "string",
"mode": "string"
},
"nsx_network": {
"namespace_network_cidrs": [
{
"address": "string",
"prefix": 0
}
],
"ingress_cidrs": [
{
"address": "string",
"prefix": 0
}
],
"egress_cidrs": [
{
"address": "string",
"prefix": 0
}
],
"nsx_tier0_gateway": "string",
"subnet_prefix_length": 0,
"routed_mode": false,
"load_balancer_size": "string"
}
},
"network_list": [
{
"network": "string",
"network_provider": "string",
"vsphere_network": {
"portgroup": "string",
"ip_assignment_mode": "string",
"address_ranges": [
{
"address": "string",
"count": 0
}
],
"gateway": "string",
"subnet_mask": "string",
"mode": "string"
},
"nsx_network": {
"namespace_network_cidrs": [
{
"address": "string",
"prefix": 0
}
],
"ingress_cidrs": [
{
"address": "string",
"prefix": 0
}
],
"egress_cidrs": [
{
"address": "string",
"prefix": 0
}
],
"nsx_tier0_gateway": "string",
"subnet_prefix_length": 0,
"routed_mode": false,
"load_balancer_size": "string"
}
}
]
},
"workload_ntp_servers": [
"string"
],
"load_balancer_config_spec": {
"id": "string",
"address_ranges": [
{
"address": "string",
"count": 0
}
],
"provider": "string",
"ha_proxy_config_create_spec": {
"servers": [
{
"host": "string",
"port": 0
}
],
"username": "string",
"password": "string",
"certificate_authority_chain": "string"
},
"avi_config_create_spec": {
"server": {
"host": "string",
"port": 0
},
"username": "string",
"password": "string",
"certificate_authority_chain": "string",
"cloud_name": "string"
}
},
"master_management_network": {
"floating_ip": "string",
"network": "string",
"network_segment": {
"networks": [
"string"
]
},
"mode": "string",
"address_range": {
"starting_address": "string",
"address_count": 0,
"subnet_mask": "string",
"gateway": "string"
}
},
"master_dns": [
"string"
],
"worker_dns": [
"string"
],
"master_dns_search_domains": [
"string"
],
"master_ntp_servers": [
"string"
],
"master_storage_policy": "string",
"ephemeral_storage_policy": "string",
"cns_file_config": {
"vsan_clusters": [
"string"
]
},
"login_banner": "string",
"master_dns_names": [
"string"
],
"image_storage": {
"storage_policy": "string"
},
"default_image_registry": {
"hostname": "string",
"port": 0
},
"default_image_repository": "string",
"default_kubernetes_service_content_library": "string",
"cluster_proxy_config": {
"proxy_settings_source": "string",
"https_proxy_config": "string",
"http_proxy_config": "string",
"no_proxy_config": [
"string"
],
"tls_root_ca_bundle": "string"
},
"content_libraries": [
{
"content_library": "string",
"supervisor_services": [
"string"
],
"resource_naming_strategy": "string"
}
],
"count": 0
}This affects the size and resources allocated to the Kubernetes API server. It also affects the suggested default serviceCidr and podCidrs.
For more information see: Vcenter NamespaceManagement SizingHint.
This property was added in vSphere API 7.0.0.0.
CIDR block from which Kubernetes allocates service cluster IP addresses. This range should not overlap with those in Vcenter NamespaceManagement Clusters NCPClusterNetworkEnableSpec.pod_cidrs, Vcenter NamespaceManagement Clusters NCPClusterNetworkEnableSpec.ingress_cidrs, Vcenter NamespaceManagement Clusters NCPClusterNetworkEnableSpec.egress_cidrs, or other services running in the datacenter.
This property was added in vSphere API 7.0.0.0.
The provider of cluster networking for this vSphere Namespaces cluster.
For more information see: Vcenter NamespaceManagement Clusters NetworkProvider.
This property was added in vSphere API 7.0.0.0.
Specification for the NSX Container Plugin cluster network.
This property was added in vSphere API 7.0.0.0.
This property is optional and it is only relevant when the value of network_provider is Vcenter NamespaceManagement Clusters NetworkProvider.NSXT_CONTAINER_PLUGIN.
Specification for the workload networks to be associated with the cluster.
This property was added in vSphere API 7.0.1.0.
This property is optional and it is only relevant when the value of network_provider is Vcenter NamespaceManagement Clusters NetworkProvider.VSPHERE_NETWORK.
List of NTP server DNS names or IP addresses to use for workloads such as Kubernetes Cluster VMs, specified in order of preference.
This property was added in vSphere API 7.0.1.0.
If missing or null, NTP server for Kubernetes API servers will be used.
The load balancer configuration is derived from the user-provisioned load balancer that will be used to operate a load balancer that fronts vSphere Namespaces cluster servers, Kubernetes Cluster API servers, and other servers upon request.
This configuration is required for network providers that do not have a default load balancer included.
This property was added in vSphere API 7.0.1.0.
This property is optional and it is only relevant when the value of network_provider is Vcenter NamespaceManagement Clusters NetworkProvider.VSPHERE_NETWORK.
Specification for the management network on Kubernetes API server. Vcenter NamespaceManagement Clusters NetworkSpec.mode must be STATICRANGE as we require Kubernetes API server to have a stable address.
This property was added in vSphere API 7.0.0.0.
List of DNS server IP addresses to use on Kubernetes API server, specified in order of preference.
This property was added in vSphere API 7.0.0.0.
If missing or null, no default DNS servers are set.
List of DNS server IP addresses to use on the worker nodes, specified in order of preference.
This property was added in vSphere API 7.0.0.0.
If missing or null, no default DNS servers are set.
List of domains (for example "vmware.com") to be searched when trying to lookup a host name on Kubernetes API server, specified in order of preference.
This property was added in vSphere API 7.0.0.0.
If missing or null, no default DNS search domains are set.
List of NTP server DNS names or IP addresses to use on Kubernetes API server, specified in order of preference.
This property was added in vSphere API 7.0.0.0.
If missing or null, VMware Tools based time synchronization is enabled.
Identifier of storage policy associated with Kubernetes API server.
This property was added in vSphere API 7.0.0.0.
When clients pass a value of this schema as a parameter, the property must be an identifier for the resource type: SpsStorageProfile. When operations return a value of this schema as a response, the property will be an identifier for the resource type: SpsStorageProfile.
Identifier of storage policy associated with ephemeral disks of all the Kubernetes Pods in the cluster.
This property was added in vSphere API 7.0.0.0.
When clients pass a value of this schema as a parameter, the property must be an identifier for the resource type: SpsStorageProfile. When operations return a value of this schema as a response, the property will be an identifier for the resource type: SpsStorageProfile.
Specification for configuring Cloud Native Storage file volume support on Supervisor. This feature provides support for provisioning ReadWriteMany persistent volumes on this cluster and/or external clusters.
This property was added in vSphere API 7.0.3.0.
If missing or null, file volume support will not be enabled on this Supervisor.
Disclaimer to be displayed prior to login via the Kubectl plugin.
This property was added in vSphere API 7.0.0.0.
If missing or null, just skip it.
List of DNS names to associate with the Kubernetes API server. These DNS names are embedded in the TLS certificate presented by the API server.
This property was added in vSphere API 7.0.0.0.
If missing or null, no DNS names are embedded in the TLS certificate.
Specification for storage to be used for container images.
This property was added in vSphere API 7.0.0.0.
Default image registry to use when Kubernetes Pod container specification does not specify it as part of the container image name.
This property was added in vSphere API 7.0.0.0.
If missing or null, defaults to Docker Hub.
Default image repository to use when Kubernetes Pod container specification does not specify it as part of the container image name.
This property was added in vSphere API 7.0.0.0.
If missing or null, defaults to Docker Hub official repository in case of Docker Hub image registry, otherwise defaults to empty string.
This property is deprecated as of vSphere API 9.0.0.0. Use Vcenter NamespaceManagement Clusters EnableSpec.content_libraries instead.
Identifier of the Content Library which holds the VM Images for vSphere Kubernetes Service.
This Content Library should be subscribed to VMware's hosted vSphere Kubernetes Service Repository.
This property was added in vSphere API 7.0.0.0.
If missing or null, the Content Library will be automatically generated and configured to the Supervisor.
When clients pass a value of this schema as a parameter, the property must be an identifier for the resource type: com.vmware.content.Library. When operations return a value of this schema as a response, the property will be an identifier for the resource type: com.vmware.content.Library.
Proxy configuration that will be applied to the Supervisor. The proxy should be reachable from the management network and will be used for image pulling and container traffic exiting out of the Supervisor.
This property was added in vSphere API 7.0.3.00100.
If missing or null the settings will be inherited from the vCenter settings if available.
List of Content Libraries that will be associated with a Supervisor. This list should refer to existing Content Libraries in the vSphere inventory. These Content Libraries and the Content Library items belonging to them will be read-only across all vSphere Namespaces. If Vcenter NamespaceManagement Clusters EnableSpec.default_kubernetes_service_content_library is set, the Content Library identifier will be migrated to this property.
This property was added in vSphere API 8.0.2.0.
If missing or null, a subscribed Content Library, subscribed to VMware's hosted vSphere Kubernetes Service Repository, will be automatically created and configured to the Supervisor.
Number of control planes requested during Supervisor enablement. The allowed values are either 1 or 3.
This property was added in vSphere API 9.0.0.0.
If missing or null, defaults to 3.